Uploaded image for project: 'Confluence Cloud'
  1. Confluence Cloud
  2. CONFCLOUD-71166

page properties report macro doesn’t show the smart link if we add any text/user after inserting the jira issue

      Issue Summary

      If we add a jira issue link in the page properties macro and mention a user, add any text or add anything in the columns in page properties table then the smart links for jira issue doesn’t show in the page properties report macro, simple issue url is displaying.

       

      Steps to Reproduce

      1. Step 1 Create page and add page properties macro on the page and insert jira issue link and then mention a user/add text in the page properties macro

      2. Step 2 add label on these page
      3. Step 3 Create another page and insert page properties report macro and filter the page by label

      Expected Results

      Page properties report macro should show the smart links of jira issue.

      Actual Results

      Normal links/url are displaying in page properties report macro.

      Note: If we add the user mention/add any text on the page and then publish the page and then add jira ticket then it seems to be working fine, there is no way to fix the links we have to reinsert the jira issue.

      Workaround

      First, insert values in all columns and then publish the page and then edit again and add the jira issues on the page, now it should show smart links.

        1. image-2020-11-18-20-03-48-889.png
          image-2020-11-18-20-03-48-889.png
          163 kB
        2. image-2020-11-18-20-41-39-996.png
          image-2020-11-18-20-41-39-996.png
          32 kB
        3. image-2020-11-18-20-42-51-913.png
          image-2020-11-18-20-42-51-913.png
          36 kB
        4. image-2020-11-25-19-21-52-900.png
          image-2020-11-25-19-21-52-900.png
          242 kB
        5. screenshot-1.png
          screenshot-1.png
          242 kB

          Form Name

            [CONFCLOUD-71166] page properties report macro doesn’t show the smart link if we add any text/user after inserting the jira issue

            Hans Fast added a comment -

            Hi,

            This bug has a wider affected area than described and is affects our workflow a lot. It makes it impossible to get a table overview from Confluence of statuses in Jira, since at any time a page in Confluence is edited, all smart links to Jira in the page properties report are lost.

            Summarize

            Any edit to a page which contains links in page properties to any Jira issue, will cause the link to be displayed as regular URL, not as a smart link. 

            Steps to Reproduce

            1. Create page A and add page properties macro on the page and insert links to Jira issues.
              The link to Jira can be inserted by copy and paste or by the Jira issue macro, does not matter.
            2. Publish page A.
            1. Create page B and insert page properties report macro.
            2. Publish page B.
              Links to Jira show as smart links with Jira Issue type, Summary, Status.
            3. Make any edit on page A and publish the page.
            4. Refresh page B.
              All smart links are replaced with regular URLs, Issue type, Summary, Status don't show any more.

            Expected Results

            Page properties report macro should show the smart links of Jira issues.

            Actual Results

            All smart links are replaced by normal links/url in page properties report macro after the page containing links has been edited.

            Workaround

            The workaround to add all Jira links last is not practical. 

             

             

            Hans Fast added a comment - Hi, This bug has a wider affected area than described and is affects our workflow a lot. It makes it impossible to get a table overview from Confluence of statuses in Jira, since at any time a page in Confluence is edited, all smart links to Jira in the page properties report are lost. Summarize Any edit to a page which contains links in page properties to any Jira issue, will cause the link to be displayed as regular URL, not as a smart link.  Steps to Reproduce Create page A and add page properties macro on the page and insert links to Jira issues. The link to Jira can be inserted by copy and paste or by the Jira issue macro, does not matter. Publish page A. Create page B and insert page properties report macro. Publish page B. Links to Jira show as smart links with Jira Issue type , Summary , Status . Make any edit on page A and publish the page. Refresh page B. All smart links are replaced with regular URLs, Issue type, Summary, Status don't show any more. Expected Results Page properties report macro should show the smart links of Jira issues. Actual Results All smart links are replaced by normal links/url in page properties report macro after the page containing links has been edited. Workaround The workaround to add all Jira links last is not practical.     

            It also affects very long links that are displayed on the subpage in the page properties as smart links and then in the page properties report as a very long link instead of a smart link. Which stretches the page properties report table way too wide.

            Enrico Skottnik added a comment - It also affects very long links that are displayed on the subpage in the page properties as smart links and then in the page properties report as a very long link instead of a smart link. Which stretches the page properties report table way too wide.

            nvanlooy added a comment -

            +1

            nvanlooy added a comment - +1

            +1

            Peter Mills added a comment - - edited

            Pieter, I take it that 'permission to create attachments' is a Jira security setting.  I don't understand why Atlassian would want to prevent contributors to an issue in this project from creating attachments?  Makes no sense - Atlassian, can we please have permission to add images to issues in this project?

            Peter Mills added a comment - - edited Pieter, I take it that 'permission to create attachments' is a Jira security setting.  I don't understand why Atlassian would want to prevent contributors to an issue in this project from creating attachments?  Makes no sense - Atlassian, can we please have permission to add images to issues in this project?

            Peter Mills, images cannot be added by issue commenters. However, you could upload the images to a service such as img.ur and paste the links instead. 

            Pieter Helsen added a comment - Peter Mills, images cannot be added by issue commenters. However, you could upload the images to a service such as img.ur and paste the links instead. 

            I tried editing my comment, but I'm getting a permissions error

            "You do not have permission to create attachments for this issue"

            Peter Mills added a comment - I tried editing my comment, but I'm getting a permissions error "You do not have permission to create attachments for this issue"

            The images are missed. Please fix it

            Andrey Markelov added a comment - The images are missed. Please fix it

            Hi Atlassian, 

            I note that the bug https://jira.atlassian.com/browse/CONFCLOUD-54631 was fixed recently, addressing the problem of multiple Jira tickets not rendering correctly.

            Unfortunately the Page Properties Report  ("PPR") macro is still not completely fixed wrt rendering single Jira tickets correctly.  Although the problem with the infinite 'spinner' has gone, single Jira tickets still render as plain text hyperlinks, not Smart links.

            To summarise, the Jira ticket when rendered inside the PPR macro should look like this 

            But instead it looks like this

            The only time the single Jira ticket renders correctly is after the Jira macro has been inserted for the first time into the Page Properties macro on the child page and the child page published.  ANY subsequent edits to the child page will result in the PPR macro reverting to displaying the plain text hyperlink.  

            Interestingly, with the recent bug fix https://jira.atlassian.com/browse/CONFCLOUD-54631 I note that the Jira ticket rendering problem only occurs for the "Single Issue" display option.  When I choose the "Table" display option, the Jira ticket always renders as expected - but being a table layout  it is not very easy on the eye - it looks like this 

            Any chance of fixing the issue with single Jira ticket rendering in the PPR macro?

             

            Cheers

            Peter

            Peter Mills added a comment - Hi Atlassian,  I note that the bug https://jira.atlassian.com/browse/CONFCLOUD-54631 was fixed recently, addressing the problem of multiple Jira tickets not rendering correctly. Unfortunately the Page Properties Report  ("PPR") macro is still not completely fixed wrt rendering single Jira tickets correctly.  Although the problem with the infinite 'spinner' has gone, single Jira tickets still render as plain text hyperlinks, not Smart links. To summarise, the Jira ticket when rendered inside the PPR macro should look like this  But instead it looks like this The only time the single Jira ticket renders correctly is after the Jira macro has been inserted for the first time into the Page Properties macro on the child page and the child page published.  ANY subsequent edits to the child page will result in the PPR macro reverting to displaying the plain text hyperlink.   Interestingly, with the recent bug fix https://jira.atlassian.com/browse/CONFCLOUD-54631 I note that the Jira ticket rendering problem only occurs for the "Single Issue" display option.  When I choose the "Table" display option, the Jira ticket always renders as expected - but being a table layout  it is not very easy on the eye - it looks like this  Any chance of fixing the issue with single Jira ticket rendering in the PPR macro?   Cheers Peter

            Would appreciate this issue being addressed. My team gathers lots of details and we use page properties to report to our customers what action they need take in Confluence. Having them click through loads of hyperlinks to get to a ticket to see a status is very unhelpful.

            glenn.unrath added a comment - Would appreciate this issue being addressed. My team gathers lots of details and we use page properties to report to our customers what action they need take in Confluence. Having them click through loads of hyperlinks to get to a ticket to see a status is very unhelpful.

              nagarwal@atlassian.com Niraj
              nghuraiya@atlassian.com Neha Ghuraiya
              Affected customers:
              76 This affects my team
              Watchers:
              48 Start watching this issue

                Created:
                Updated:
                Resolved: